Registrant defined prerequisites for registering a tertiary domain

ABSTRACT

Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: receive, from a sub domain registration settings control panel displayed on a client computer, rule or prerequisites required for a sub domain registrant to register a sub domain, and store these rules or prerequisites in a database. The server(s) may then receive: a sub domain registration request, an IP address directing HTTP requests to the sub domain; and an authentication verifying that the prerequisite has been fulfilled. If authenticated, the server(s) may automatically insert the IP address into an A record or NS record in a zone file for the domain.

FIELD OF THE INVENTION

The present invention generally relates to the field of Domain Nameregistration and specifically to: registering a tertiary domain of anassociated domain name via an automated registrar framework; sharing,with a registrant of the domain name, revenue received from the tertiarydomain registration; defining, according to registrant input,prerequisites for registering the tertiary domain; and defining,according to registrant input, tertiary domain control panel and updatefeatures available to the sub domain registrant.

SUMMARY OF THE INVENTION

The present invention provides systems and methods comprising one ormore server computers communicatively coupled to a network and includinginstructions, that when executed by a processor running on the one ormore server computers, cause the one or more server computers to:receive, from a sub domain registration settings control panel displayedon a client computer, a profit to be paid to a registrant if a subdomain associated with the domain name is registered, and store theprofit to be paid in a database. The server(s) may also render a subdomain registration control panel and receive: a sub domain registrationrequest; and an IP address directing HTTP requests to the sub domain andautomatically insert the IP address into an A record or NS record in azone file for the domain. The server(s) may then select the profit to bepaid from the database and update a registrant user profile to includethe profit to be paid.

In another embodiment, the present invention provides systems andmethods comprising one or more server computers communicatively coupledto a network and including instructions, that when executed by aprocessor running on the one or more server computers, cause the one ormore server computers to: receive, from a sub domain registrationsettings control panel displayed on a client computer, rule orprerequisites required for a sub domain registrant to register a subdomain, and store these rules or prerequisites in a database. Theserver(s) may then receive: a sub domain registration request, an IPaddress directing HTTP requests to the sub domain; and an authenticationverifying that the prerequisite has been fulfilled. If authenticated,the server(s) may automatically insert the IP address into an A recordor NS record in a zone file for the domain.

In another embodiment, the present invention provides systems andmethods comprising one or more server computers communicatively coupledto a network and including instructions, that when executed by aprocessor running on the one or more server computers, cause the one ormore server computers to: receive, from a sub domain registrationsettings control panel displayed on a client computer, form elements tobe displayed on a sub domain settings control panel, and store theseform elements in a database. The server(s) may then display an HTML formon the sub domain settings control panel, where each HTML for elementcorresponds to a database record defining features for updating anemail, tertiary domain or record modification to a zone file for aregistered sub domain.

The above features and advantages of the present invention will bebetter understood from the following detailed description taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example embodiment including a user interface demonstratinga zone file.

FIG. 2 is an example embodiment including a user interface used inregistering a domain name.

FIG. 3 illustrates a possible system for registering a tertiary domainname with revenue sharing and registrant controls.

FIG. 4 illustrates a more detailed possible system for registering atertiary domain name with revenue sharing and registrant controls.

FIG. 5 is an example embodiment including a user interface used inregistering a tertiary domain name with revenue sharing and registrantcontrols.

FIG. 6 is a flow diagram illustrating a possible embodiment of a methodfor registering a tertiary domain name with revenue sharing andregistrant controls.

FIG. 7 is a flow diagram illustrating a possible embodiment of a methodfor registering a tertiary domain name with revenue sharing andregistrant controls.

FIG. 8 is a flow diagram illustrating a possible embodiment of a methodfor registering a tertiary domain name with revenue sharing andregistrant controls.

FIG. 9 is a example embodiment including a user interface used inregistering a tertiary domain name with revenue sharing and registrantcontrols.

FIG. 10 is a example embodiment including a user interface used inregistering a tertiary domain name with revenue sharing and registrantcontrols.

DETAILED DESCRIPTION

The present inventions will now be discussed in detail with regard tothe attached drawing figures that were briefly described above. In thefollowing description, numerous specific details are set forthillustrating the Applicant's best mode for practicing the invention andenabling one of ordinary skill in the art to make and use the invention.It will be obvious, however, to one skilled in the art that the presentinvention may be practiced without many of these specific details. Inother instances, well-known machines, structures, and method steps havenot been described in particular detail in order to avoid unnecessarilyobscuring the present invention. Unless otherwise indicated, like partsand method steps are referred to with like reference numerals.

A network is a collection of links and nodes (e.g., multiple computersand/or other devices connected together) arranged so that informationmay be passed from one part of the network to another over multiplelinks and through various nodes. Examples of networks include theInternet, the public switched telephone network, the global Telexnetwork, computer networks (e.g., an intranet, an extranet, a local-areanetwork, or a wide-area network), wired networks, and wireless networks.

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweencomputer users. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information (e.g.,text, graphics, audio, video, animation, and other forms of data) atspecific locations on the Internet referred to as websites. Thecombination of all the websites and their corresponding web pages on theInternet is generally known as the World Wide Web (WWW) or simply theWeb.

Prevalent on the Web are multimedia websites, some of which may offerand sell goods and services to individuals and organizations. Websitesmay consist of a single webpage, but typically consist of multipleinterconnected and related web pages. Websites, unless extremely largeand complex or have unusual traffic demands, typically reside on asingle server and are prepared and maintained by a single individual orentity. Website browsers are able to locate specific websites becauseeach website, resource, and computer on the Internet has a uniqueInternet Protocol (IP) address.

IP addresses, however, even in human readable notation, are difficultfor people to remember and use. A Uniform Resource Locator (URL) is mucheasier to remember and may be used to point to any computer, directory,or file on the Internet. A browser is able to access a website on theInternet through the use of a URL. The URL may include a HypertextTransfer Protocol (HTTP) request combined with the website's Internetaddress, also known as the website's domain name.

Domain names are much easier to remember and use than theircorresponding IP addresses. The Internet Corporation for Assigned Namesand Numbers (ICANN) approves some Generic Top-Level Domains (gTLD) anddelegates the responsibility to a particular organization (a “registry”)for maintaining an authoritative source for the registered domain nameswithin a TLD and their corresponding IP addresses.

The Domain Name System (DNS) is the world's largest distributedcomputing system that enables access to any resource in the Internet bytranslating user-friendly domain names to IP Addresses. The Internetmaintains two principal namespaces: the domain name hierarchy and the IPaddress system. The DNS maintains the domain namespace and providestranslation services between these two namespaces.

The process of translating domain names to IP Addresses is called nameresolution. A DNS name resolution is the first step in the majority ofInternet transactions. This DNS provides name resolution service througha family of servers called domain name servers. The DNS resolution takesplace transparently in response to a sent resolution request withinapplications such as web browsers, e-mail clients, and other Internetapplications residing in a local operating system. These applicationshandle the required communications.

The authoritative data needed for performing the name resolution serviceis controlled by a name server, which contains the information for thezone for the domain name. In some instances, this information iscontained in a file called the zone file. A zone file for the domainname example.com is seen in FIG. 1. The hierarchical domain space isdivided into administrative units called zones, and a zone usuallyconsists of a domain (e.g., example.com) and possibly one or more subdomains or other tertiary domain names (e.g., projects.example.com,services.example.com). As used in this specification, a domain name(e.g., example.com) may comprise a second level domain (SLD)concatenated to a top level domain (TLD), and a sub domain or tertiarydomain may comprise any domains beyond the SLD (e.g.,spreadsheet.example.com, columns.spreadsheet.example.com, etc.)

Sometimes sub domains are records in the zone, such as A records orCNAME records, and sometimes they are relegated to another name server.In the context of the current application, this is a significantdistinction, as the registration of sub domains in the currentapplication is accomplished via name server delegation of sub domains.For example, in the zone file for xyz.com, foo as a CNAME record or an Arecord simply defines a record of a type. However, foo in xyz.com as anNS record delegates the entire zone to a new name server.

Zone files may include a collection of DNS records such as resourcerecords. A resource record is the basic data element in the DNS, andeach resource record has a type, examples of which include addressrecords (A, AAAA), name server records (NS), and mail exchanger records(MX) for a domain name. Each record may also include an expiration timelimit, a class, and some type-specific data. Each record may alsoinclude various fields, such as NAME (a fully qualified domain name ofthe node in the hierarchy tree), TYPE (format of data for intended use,e.g., NS or MX servers), RDATA (e.g., IP addresses for address records),CLASS (e.g., IN for internet), etc. Resource records of the same typedefine a resource record set.

FIG. 2 shows a simplified example means for a user to register a domainname. In this example, a representative of the Chamber of Commerce forthe city of Flagstaff desires to register the domain name flagstaff.com.This representative, now a potential domain name registrant, may accessa web page of a domain name registrar, and search the availability ofthe desired domain name, flagstaff.com. The registrar web page may be adomain name control panel rendered by one or more servers operated bythe registrar. These servers may transmit the rendered control panel toone or more client computers operated by the potential registrant. Theclient(s) may receive the rendered control panel and display it on aclient display software, such as an Internet browser. This domain namecontrol panel may include one or more user interface controls, such asHTML form elements, for receiving encoded data necessary for searchingand/or requesting registration of a domain name. The domain nameregistrant may then transmit the domain name registration data to theregistrar server(s).

The registrar's server(s) may search and determine the availability ofthe requested domain name, possibly by searching registrar/registrydatabase records and/or zone files in the registry to determine theavailability of the desired top level domain. If the requested domain isnot found in the database records or zone files, and therefore notavailable, the registrar server(s) may transmit a notification to theclient that the requested domain name is not available and the potentialregistrant may restart the process, entering a different domain name inthe search field. However, if the requested domain name is available,the registrar server(s) may transmit a notification that the requesteddomain name is available and that the potential registrant shouldproceed with the registration process.

In the example in FIG. 2, on learning that flagstaff.com is available,the potential registrant may input a plurality of data into the controlpanel, possibly including registration information (e.g., registrantname and contact information, such as email, to be stored in a WHOISdatabase), pay a fee and receive notice that the domain name has beenregistered.

The registrar may then pay any required fees, update the WHOIS database,and follow any additional requirements of the registry or any additionalauthorities such as ICANN, to register the domain name. The registrarmay then create a zone file for the registered domain name, and updatethe registry with the name server for the newly created zone file.

The disclosed invention improves on the current domain name registrationmodel by providing means for the domain name registrant to sub registersub domains to a sub domain registrant, utilizing a registrar'sframework to automatically update the existing DNS framework and theregistrar's existing proprietary data. As non-limiting examples, thisautomatic update may include inserting an A record identifying an IPaddress for the sub domain, into the zone file for the domain name.Alternatively, the automatic update may include generating an entirelynew zone file for the sub domain defining the DNS provider of the subdomain, possibly including an A record identifying the IP address forthe sub domain. The automatic update may also include inserting an NSrecord into the zone file for the domain name, identifying the DNSprovider for the sub domain via the newly created sub domain zone file.The automatic update may also include the registrar updating datarecords to track the sub domain registrations in association with theregistered domain name.

The disclosed invention also improves on the current domain nameregistration model by creating a revenue sharing business model,allowing a domain name registrant to monetize their domain name. In thisrevenue sharing business model, the registrar may require certain fixedcosts to execute the automatic framework to sub register sub domains, asdescribed above. The registrar may identify these fixed costs, andrequire a fee to cover these costs from the domain name registrant foreach sub domain registration transaction. However, the registrar mayalso provide means for the domain name registrant, possibly via userinput through a sub domain registration settings control panel, toidentify a registrant-defined fee associated with each sub domainregistration. The registrar may then include a profit margin, withinthat fee, that the registrant will receive as each sub domain isregistered.

For example, a domain name registrant, an Arizona Cardinals fan, mayregister the domain name cardinalfan.com. The registrant may then set upany desired sub domains to be used within the domain name for theregistrant's purposes (e.g., admin.cardinalfan.com,stats.cardinalfan.com). The registrant may then desire to monetize thedomain name by charging a fee above the registrar's fixed costs toregister sub domains to other Cardinals fans, such asarnold.cardinalfan.com, andrew.cardinalfan.com orredandwhite.cardinalfan.com. However, the registrant may not want todeal with the recordkeeping or administration of DNS settings, databaserecords, keeping track of fees for registering the sub domains, etc. Thedisclosed invention, therefore, provides means for a registrar toadministrate all DNS settings, record keeping, and fee management forsuch a domain name registrant while providing a revenue sharing modelwith the registrant.

The disclosed invention also improves on the current domain nameregistration model by providing means, possibly through a sub domainregistration settings control panel, for the domain name registrant todefine one or more rules and/or prerequisites that must be fulfilledbefore a sub domain registrant is qualified to register the sub domain.Continuing the example of the Flagstaff Chamber of Commerce above, theChamber of Commerce may want to promote the city through a .com website,but may not want businesses outside of the Flagstaff city limits toregister these sub domains. For example, the Chamber of Commerce maywant to promote Flagstaff businesses by encouraging these businesses toregister sub domains such as joespizza.flagstaff.com,drugstore.flagstaff.com, etc. The city, in this example, may thereforeprovide these businesses with a code enabling them to register subdomains. In this example, the city may provide an alphanumeric code tobusinesses within the city limits, which the business representativewill input into, for example, a sub domain registration control panel,in order to validate the business representative in order to register asub domain.

The disclosed invention also improves on the current domain nameregistration model by providing means for the domain name registrant todefine one or more features on, for example, a sub domain settingscontrol panel made available to the sub domain registrant afterregistering the sub domain. For example, the Chamber of Commerce mayhave security concerns about providing sub domain registrants with theability to create sub domain email addresses (e.g., phishing scamssucceeding due to confusion with the flagstaff.com domain name) or aboutproviding sub domain registrants access to the domain name or sub domainzone files (e.g., as a possible avenue for hackers.). The city maytherefore define, possibly through a sub domain registration settingscontrol panel, limitations on the features available to sub domainregistrants in association with their registered sub domains.

Several different environments may be used to accomplish the methodsteps of embodiments disclosed herein. FIG. 1 demonstrates a streamlinedexample and FIG. 2 demonstrates a more detailed example of anenvironment including a system and/or structure that may be used toaccomplish the methods and embodiments disclosed and described herein.Such methods may be performed by any central processing unit (CPU) inany computing system, such as a microprocessor running on at least oneserver 310 and/or client 320, and executing instructions stored (perhapsas scripts and/or software, possibly as software modules/components) incomputer-readable media accessible to the CPU, such as a hard disk driveon a server 310 and/or client 320. The example embodiments herein placeno limitations on whom or what may comprise users. Thus, as non-limitingexamples, users may comprise any individual, entity, business,corporation, partnership, organization, governmental entity, and/oreducational institution.

The example embodiments shown and described herein exist within theframework of a network 300 and should not limit possible networkconfiguration or connectivity. Such a network 300 may comprise, asnon-limiting examples, any combination of the Internet, the publicswitched telephone network, the global Telex network, computer networks(e.g., an intranet, an extranet, a local-area network, or a wide-areanetwork), a wired network, a wireless network, a telephone network, acorporate network backbone or any other combination of known or laterdeveloped networks. At least one server 310 and at least one client 320may be communicatively coupled to the network 300via any method ofnetwork connection known in the art or developed in the futureincluding, but not limited to wired, wireless, modem, dial-up,satellite, cable modem, Digital Subscriber Line (DSL), AsymmetricDigital Subscribers Line (ASDL), Virtual Private Network (VPN),Integrated Services Digital Network (ISDN), X.25, Ethernet, token ring,Fiber Distributed Data Interface (FDDI), IP over Asynchronous TransferMode (ATM), Infrared Data Association (IrDA), wireless, WAN technologies(T1, Frame Relay), Point-to-Point Protocol over Ethernet (PPPoE), and/orany combination thereof.

Server(s) 310 may comprise any computer or program that providesservices to other computers, programs, or users either in the samecomputer or over a computer network 300. As non-limiting examples, theserver 310 may comprise application, communication, mail, database,proxy, fax, file, media, web, peer-to-peer, standalone, software, orhardware servers (i.e., server computers) and may use any server formatknown in the art or developed in the future (possibly a shared hostingserver, a virtual dedicated hosting server, a dedicated hosting server,a cloud hosting solution, a grid hosting solution, or any combinationthereof) and may be used, for example to provide access to the dataneeded for the software combination requested by a client 320.

The server 310 may exist within a server cluster, as illustrated. Theseclusters may include a group of tightly coupled computers that worktogether so that in many respects they can be viewed as though they area single computer. The components may be connected to each other throughfast local area networks which may improve performance and/oravailability over that provided by a single computer.

The client 320 may be any computer or program that provides services toother computers, programs, or users either in the same computer or overa computer network 300. As non-limiting examples, the client 320 may bean application, communication, mail, database, proxy, fax, file, media,web, peer-to-peer, or standalone computer, cell phone, personal digitalassistant (PDA), etc. which may contain an operating system, a full filesystem, a plurality of other necessary utilities or applications or anycombination thereof on the client 320. Non limiting example programmingenvironments for client applications may include JavaScript/AJAX (clientside automation), ASP, JSP, Ruby on Rails, Python's Django, PHP, HTMLpages or rich media like Flash, Flex or Silverlight. The client(s) 320that may be used to connect to the network 300 to accomplish theillustrated embodiments may include, but are not limited to, a desktopcomputer, a laptop computer, a hand held computer, a terminal, atelevision, a television set top box, a cellular phone, a wirelessphone, a wireless hand held device, an Internet access device, a richclient, thin client, or any other client functional with a client/servercomputing architecture. Client software may be used for authenticatedremote access to a hosting computer or server. These may be, but are notlimited to being accessed by a remote desktop program and/or a webbrowser, as are known in the art.

The user interface displayed on the client(s) 320 or the server(s) 310may be any graphical, textual, scanned and/or auditory information acomputer program presents to the user, and the control sequences such askeystrokes, movements of the computer mouse, selections with a touchscreen, scanned information etc. used to control the program. Examplesof such interfaces include any known or later developed combination ofGraphical User Interfaces (GUI) or Web-based user interfaces as seen inthe accompanying drawings, Touch interfaces, Conversational InterfaceAgents, Live User Interfaces (LUI), Command line interfaces, Non-commanduser interfaces, Object-oriented User Interfaces (OOUI) or Voice userinterfaces. The commands received within the software combination, orany other information, may be accepted using any field, widget and/orcontrol used in such interfaces, including but not limited to atext-box, text field, button, hyper-link, list, drop-down list,check-box, radio button, data grid, icon, graphical image, embeddedlink, etc.

Data storage 330 may be communicatively coupled to the network 300 andmay include any information requested or required by the system and/ordescribed herein. The data storage 330 may be any computer components,devices, and/or recording media that may retain digital data used forcomputing for some interval of time. The storage may be capable ofretaining stored content for any data required, on a single machine orin a cluster of computers over the network 300, in separate memory areasof the same machine such as different hard drives, or in separatepartitions within the same hard drive, such as a database partition.Structurally, the data storage 330 may comprise any collection of data.As non-limiting examples, the data storage 330 may comprise a localdatabase, online database, desktop database, server-side database,relational database, hierarchical database, network database, objectdatabase, object-relational database, associative database,concept-oriented database, entity-attribute-value database,multi-dimensional database, semi-structured database, star schemadatabase, XML database, file, collection of files, spreadsheet, and/orother means of data storage such as a magnetic media, hard drive, otherdisk drive, volatile memory (e.g., RAM), non-volatile memory (e.g., ROMor flash), and/or any combination thereof.

Non-limiting examples of the data storage 330 may include, but are notlimited to, a Network Area Storage, (“NAS”), which may be aself-contained file level computer data storage connected to andsupplying a computer network with file-based data storage services. Thestorage subsystem may also be a Storage Area Network (“SAN”—anarchitecture to attach remote computer storage devices to servers insuch a way that the devices appear as locally attached), an NAS-SANhybrid, any other means of central/shared storage now known or laterdeveloped or any combination thereof.

The server(s) 310 or software modules within the server(s) 310 may usequery languages such as MSSQL or MySQL to retrieve the content from thedata storage 330. Server-side scripting languages such as ASP, PHP,CGI/Perl, proprietary scripting software/modules/components etc. may beused to process the retrieved data. The retrieved data may be analyzedin order to determine the actions to be taken by the scripting language,including executing any method steps disclosed herein.

The software modules/components of the software combination used in thecontext of the current invention may be stored in the memory of—and runon—at least one server 310. As non-limiting examples of such software,the paragraphs below describe in detail the software modules/componentsthat make up the software combination. These software modules/componentsmay comprise software and/or scripts containing instructions that, whenexecuted by a microprocessor on a server 310 or client 320, cause themicroprocessor to accomplish the purpose of the module/component asdescribed in detail herein. The software combination may also shareinformation, including data from data sources and/or variables used invarious algorithms executed on the servers 310 and/or clients 320 withinthe system, between each module/component of the software combination asneeded.

A data center 340 may provide hosting services for the softwarecombination, or any related hosted website including, but not limited tohosting one or more computers or servers in a data center 340 as well asproviding the general infrastructure necessary to offer hosting servicesto Internet users including hardware, software, Internet web sites,hosting servers, and electronic communication means necessary to connectmultiple computers and/or servers to the Internet or any other network300.

Server(s) 310 may be hosted by any entity, possibly a hosting provider,a domain name registrar, a website development company, any othersoftware service provider or any combination thereof. To manage users ofsuch a system, including individuals or organizations, server(s) 310 mayhost and run a user administration program such as GODADDY's MY ACCOUNTcontrol panel for management of hosting and domain names, as anon-limiting example. In such an administration control panel program,or admin, each user may be assigned a user id. This user id may identifytransactions performed by each user. These transactions may be stored asdata records in data storage 330, each data record including the user idto associate the user with the transaction in data storage 330.

FIG. 4 shows a more detailed example embodiment of an environment forthe systems, and for accomplishing the method steps, disclosed herein.As non-limiting examples, all disclosed software modules may run on oneor more server(s) 310 and may include one or more user interfacesgenerated by the server(s) 310 and transmitted to and displayed on theclient(s) 320. The user interface(s) may be configured to receive inputfrom the user and transmit this input to the server(s) 310 for theadministration and execution of the software, using data in data storage330 associated with the software modules. Thus, the disclosed system maybe configured to execute any or all of the method steps disclosedherein.

The systems and methods disclosed in FIGS. 4-10 may provide means for adomain name registrant to register sub domains to a sub domainregistrant, and to automatically update the existing DNS framework andthe registrar's existing proprietary data and framework accordingly.Server(s) 310 may render the sub domain registration settings controlpanel 400, such as that seen in FIG. 5, and transmit it to client(s)320, which may display it on an Internet browser. The sub domainregistration settings control panel 400 may comprise a plurality of, andany combination of, HTML form elements (e.g., checkbox, slider, radiobutton, drop down box, text box, text area, etc.) In the exampleembodiment in FIG. 5, the registrant has registered the domain nameflagstaff.com using any of the registration techniques described herein.

The sub domain registration settings control panel 400 seen in FIG. 5includes means for the registrant to define each of: the revenue sharingbusiness model; one or more rules and/or prerequisites that must befulfilled before a sub domain registrant is qualified to register thesub domain; and one or more features on, for example, a sub domainsettings control panel made available to the sub domain registrant afterregistering the sub domain. However, in different embodiments, each ofthese features may appear on separate control panels, or any combinationof these features may appear on a separate control panel.

The systems and methods disclosed in FIGS. 4, 5 and 6 also provide meansto create a revenue sharing business model, allowing a domain nameregistrant to monetize their domain name. In this revenue sharingbusiness model, the registrar may require certain fixed costs to executethe automatic framework used to sub register sub domains as describedabove. The registrar may identify these fixed costs, and require themfrom the domain name registrant for each sub domain registrationtransaction. However, the registrar may also provide means for thedomain name registrant, possibly via user input through a sub domainregistration settings control panel 400, to identify aregistrant-defined fee associated with each sub domain registration. Theregistrar may then include a profit margin, within that fee, that theregistrant will receive as each sub domain is registered.

Multiple business models may be used to accomplish the monetization ofthe domain name through sub domain registration. For example, a domainname registrar may follow any of the disclosed registration proceduresto register a domain name in the name of the registrar. The registrarmay then sub register sub domains associated with the registered domainname to a plurality of sub domain registrants, and charge each of thesub domain registrants a fee. Any difference between the fee charged andthe operating costs may represent a profit to the registrar.

In another, revenue sharing, business model to monetize the domain name,a domain name registrant, possibly a customer of the registrar, mayfollow any of the disclosed registration procedures to register a domainname. Under the revenue sharing model, the registrar may provide theregistrant with a sub domain registration settings control panel 400,such as that seen in FIG. 5, to define the amount charged to sub domainregistrants. The difference between the amount the registrant chargesand the amount required by the registrar for fixed costs represents theprofit margin available to the registrant from the revenue share.

The content for the sub domain registration settings control panel 400may display the required registrar costs (e.g., for each sub domainregistered, a fee of $1.00 will be charged to the account associatedwith the registered domain name). In some embodiments, the domain nameregistrant may desire to not charge the sub domain registrants. In theseembodiments, the displayed fee for each registered sub domain will becharged to a user profile account for the registrant. Continuing theexample above, the Flagstaff Chamber of Commerce may want to promote thetown without charging local businesses to register sub domains. In thiscase, the registrant may opt out of the revenue sharing business model.In the example control panel in FIG. 5, this may be accomplished byselecting the checkbox to charge the registrar's fixed costs to aFlagstaff Chamber of Commerce user profile account. By selecting thischeckbox, or in some embodiments, by not entering the desired profitmargin, the registrant may indicate their intent to pay a fee coveringthe registrar costs.

The sub domain registration settings control panel 400 may also includean HTML form element allowing the registrant to specify a desired profitmargin comprising the amount over the required registrar costs that theregistrant wants to receive in the revenue sharing model. On submissionof the HTML form data and transmission from client(s) 320 to server(s)310, server(s) 310 may execute a database query inserting or updating aBoolean value (e.g., true or false) in a data record associated with theregistrant and/or domain name, indicating the registrant's intent, orlack thereof, to participate in the revenue sharing model. In thoseembodiments where the registrant selects to participate, the server mayinclude within the query (or run an additional query to insert) theamount of the profit margin the registrant wants to receive in therevenue sharing model.

FIG. 6 shows a flow diagram illustrating the method steps forestablishing the revenue sharing program. In step 600, server(s) 310render a sub domain registration settings control panel 400 comprising afirst HTML form and transmit the sub domain registration settingscontrol panel 400, through the network 300, to a first client computer320 for display on a first Internet browser running on the first clientcomputer 320. In step 610, server(s) 310 receive, from a registrant of adomain name, via the first HTML form, a profit to be paid in response toa sub domain being registered in association with the domain name. Instep 620, server(s) 310 execute a database query storing, within adatabase 330 coupled to the network 300, the profit to be paid. In step630, server(s) 310 render a sub domain registration control panel 405comprising a second HTML form and transmit the sub domain registrationcontrol panel 405, through the network 300, to a second client computer320 for display on a second Internet browser running on the secondclient computer 320. In step 640, server(s) 310 receive, from a subdomain registrant via the second HTML form, a transmission encoding: asub domain registration request; the sub domain to be registered inassociation with the domain name; and an IP address to which a DNSdirects an HTTP request for the sub domain. In step 650, server(s) 310execute an automated DNS command inserting: the IP address into anaddress record within a zone file for the domain name; or a name serverrecord within the zone file for the domain name. In step 660, server(s)310 execute a database query selecting the profit to be paid. In step670, server(s) 310 execute a database query storing, within a userprofile record 410 associated with the registrant, the profit to bepaid.

In some embodiments, described in more detail below, the sub domainregistration settings control panel 400 may include one or more HTMLform elements representing prerequisites required by the registrarbefore the registrant is able to register sub domains and/or affect anyupdates to the sub domain registration settings in the sub domainregistration settings control panel 400. As a non-limiting example,because each of the registered sub domains depends on the domain namebeing actively registered and maintained, surrender of the domain nameby the registrant could have catastrophic consequences on the sub domainregistrants.

The registrar may therefore provide a service ensuring stability in theregistered domain name, wherein, if the domain name registrantsurrenders the domain name (e.g., by not paying fees, attempting totransfer the domain name, changing contact data in WHOIS records, etc.),server(s) 310 may determine if the domain name is currently registeredto the registrant. If not, server(s) 310 may automatically generate andexecute commands to update the domain name account and any relatedrecords and administration (e.g., registry records, registrant records,WHOIS information, zone files, DNS records, etc.) to transfer the domainname to the registrar. The sub domain registration settings controlpanel 400 may therefore include one or more HTML form elements requiringthe registrant to agree to the transfer of the domain name in the eventof a domain name surrender before the registrant is allowed to makechanges within the control panel 400, and/or prior to sub domains beingregistered in association with the domain name.

On submission of the HTML form data and transmission from client(s) 320to server(s) 110, server(s) 310 may execute a database query insertingor updating a Boolean value (e.g., true or false) in a data recordassociated with the registrant and/or domain name, indicating theregistrant's, confirmation, or lack thereof, to automatically transferthe domain name from the registrant to the registrar if the registrantno longer administrates the domain name. In embodiments where thisconfirmation is received (i.e., server(s) 310 query a database andconfirm a true value associated in the database with the registrantand/or domain name), server(s) 310 may monitor domain name related data(e.g., WHOIS records, registrar billing records, registrar domain namedata records, etc.) to determine if the domain name is currentlyregistered to the registrant. If not, server(s) 310 may automaticallygenerate and execute commands to automatically transfer the domain nameaccount and any related records and administration (e.g., registryrecords, registrant records, WHOIS information, DNS records, zone files,etc.) to reflect the registrar as the new registrant of the domain name.

The systems and methods disclosed in FIGS. 4, 5 and 7 also providemeans, possibly through sub domain registration settings control panel400, for the domain name registrant to define one or more rules 420, theparameters of these rules 425 and/or one or more prerequisites 425 thatmust be fulfilled before a sub domain registrant is qualified toregister the sub domain. The sub domain registration settings controlpanel 400 may include any combination of HTML form elements allowing theregistrant to define the rules 415 and/or rule parameters 420 associatedwith the one or more prerequisites 425 required of a sub domainregistrant before they are enabled to register a sub domain related tothe domain name.

The example embodiment in FIG. 5 reflects the example above, where theFlagstaff Chamber of Commerce wants to limit sub domain registrationsonly to businesses within the Flagstaff city limits. The Chamber ofCommerce may therefore provide these businesses with an alphanumericcode, possibly via SMS message, email, postcard, phone call, etc. Theregistrant may therefore select the rules 415 and/or rule parameters 420associated with prerequisites 425 required by the sub domain registrantprior to registering a sub domain name. On submission of the HTML formdata and transmission from client(s) 320 to server(s) 110, server(s) 310may execute a database query inserting, for each of the defined rules415, parameters 420, and/or prerequisites 425, a data record, associatedwith the domain name and/or registrant, into a database table definingthe prerequisites.

The rules 415, parameters 420 and/or prerequisites 425 may bepredetermined and offered to the registrant, as seen in FIG. 5, or maybe defined by the registrant according to registrant-specificcustomizations (not shown). For example, the sub domain registrationsettings control panel may have a collection of pre-defined parameters420, stored in database 330, that a user may select from to define therules 415 verifying the registrant for sub domain registration. In someof these embodiments, the parameters 420 may be even more fine tuned, sothat server(s) 310 may determine if the registrant is authenticated toregister a sub domain.

Continuing the example above, the Flagstaff Chamber of Commerce, inaddition to requiring a provided code, may also want to ensure that theuser has a valid email address to which the Chamber of Commerce may sendnotifications, etc. The rules 415 may therefore be defined withparameters 420 requiring each potential sub domain registrant to providea valid email address as a prerequisite 420 to registering the desiredsub domain. The rules 415 may include additional parameters 420 toensure that the email address is a valid email address (e.g.,determining whether the email contains ‘@,’ ‘.,’ a valid domain name,etc.).

In some embodiments, the rules 415 and or parameters 420 may becustomized via customized computer code, via executable files, scripts,browser plug-ins, application programming interfaces (API), etc.Provided by the registrant. Continuing the example above, the Chamber ofCommerce may desire that the potential sub domain registrant upload ascanned copy of their business license to prove that their business iswithin the Flagstaff city limits. The registrant in this instance mayprovide custom software programming, or software instructions to accessan API, to define the rules 415 and the customized parameters 420required as prerequisites 425 for sub domain registration. These may bestored in data storage 330.

FIG. 7 shows a flow diagram illustrating the method steps forauthenticating a potential sub domain registrant according to the rules415, rule parameters 420, and/or prerequisites 425 to register a subdomain. In step 600, server(s) 310 render a sub domain registrationsettings control panel 400 comprising a first HTML form, and transmitthe sub domain registration settings control panel 400, through thenetwork 300, to a first client computer 320 for display on a firstInternet browser running on the first client computer 320. In step 700,server(s) 310 receive, from a registrant of a domain name, via the HTMLform, at least one user data defining at least one rule or prerequisitethat must be fulfilled prior to a sub domain registrant being qualifiedto register the sub domain. In step 710, server(s) 310 execute adatabase query storing, within a database coupled to the network, the atleast one user data defining the at least one rule or prerequisite. Instep 630, server(s) 310 render a sub domain registration control panelcomprising a second HTML form and transmit the sub domain registrationcontrol panel 405, through the network 300, to a second client computer320 for display on a second Internet browser running on the secondclient computer 320. In step 640, server(s) 310 receive, from a subdomain registrant via the second HTML form, a transmission encoding: asub domain registration request; the sub domain to be registered inassociation with the domain name; and an IP address to which a DNSdirects an HTTP request for the sub domain. In step 720, server(s) 310receive, from a sub domain registrant via the second HTML form, atransmission encoding an authentication verifying that the prerequisite425 has been fulfilled. In step 730, responsive to receiving theauthentication, server(s) 310 execute an automated DNS command insertingthe IP address into an address record within a zone file for the domainname; or a name server record within the zone file for the domain name.

In some embodiments, the authentication verifying that the prerequisite425 has been fulfilled may be in the form of a challenge presented tothe potential sub domain registrant. In these embodiments, server(s) 310may generate a challenge, such as a request for a code, valid email,uploaded document, challenge question, CAPTCHA, etc. and transmit it toclient(s) 320 for display. The sub domain registration control panel400, or other client display interface, may receive the response to thechallenge, and transmit it to server(s) 310, which may compare theresponse to a valid response 430 stored in data storage 330.

If the user response matches the valid response 430 in data storage, andis otherwise valid according to the rules 415, server(s) 310 may proceedwith the sub domain registration as disclosed herein. If the response isnot valid, server(s) 310 may generate a notification that the responseis not valid, and transmit it to client(s) 320 for display, possiblyincluding an additional challenge.

The systems and methods disclosed in FIGS. 4, 5, 8 and 10 also providemeans, possibly through sub domain registration settings control panel400, for the domain name registrant to define one or more features madeavailable to the sub domain registrant, possibly on a sub domainsettings control panel 435, after registering the sub domain. The subdomain registration settings control panel 400 may include anycombination of HTML form elements allowing the registrant to select ordeselect features of registered sub domains that are available to subdomain registrants via the sub domain settings control panel 435.

The example embodiment in FIG. 5 reflects the example above, where theFlagstaff Chamber of Commerce wants, for security reasons, to limit thesub domain features available to the sub domain registrant. In someembodiments, these features are limited by controlling the HTML formelements displayed on a sub domain settings control panel 435. As seenin FIG. 5, the registrant may select which HTML form elements will bedisplayed on the sub domain settings control panel 435, and byextension, which sub domain settings will be available to the sub domainregistrant for update. On submission of the HTML form data andtransmission from client(s) 320 to server(s) 110, server(s) 310 mayexecute a database query inserting, for each of the registrantselections 440, associated with the domain name and/or registrant, intoa database table defining the available update features in the subdomain control panel 435. In some embodiments, the registrant selections440 may be stored as Boolean value (e.g., true or false), which mayreflect which update features will be made available to the sub domainregistrants.

FIG. 8 shows a flow diagram illustrating the method steps fordetermining and applying the update features available to the sub domainregistrant via a sub domain control panel 435. In step 600, server(s)310 render a sub domain registration settings control panel 400comprising a first HTML form and transmit the sub domain registrationsettings control panel 400, through the network 300, to a first clientcomputer 320 for display on a first Internet browser running on thefirst client computer 320. In step 800, server(s) 310 receive, from aregistrant of a domain name, via the HTML form, at least one formelement 440 to be displayed on a second HTML form on a sub domainsetting control panel 435, the at least one form element representing asub domain update feature available to a sub domain registrant. In step810, server(s) 310 execute a database query storing, within a database330 coupled to the network 300, the at least one sub domain updatefeature available to the sub domain registrant. In step 820, server(s)310 execute a database query selecting the at least one sub domainupdate feature 440 available to sub domain registrant. In steps 830 and840, server(s) 310 render the sub domain settings control panel 435comprising the second HTML form and the at least one HTML form elementfor each sub domain update feature available 440 to the sub domainregistrant, and transmit the sub domain settings control panel 435,through the network 300, to a second client computer 320 for display ona second Internet browser running on the second client computer 320. Instep 850, server(s) 310 receive, from a sub domain registrant via thesecond HTML form, a transmission encoding: a sub domain zone file updaterequest; and an email address, a tertiary domain, or a DNS recordmodification to be updated within a sub domain zone file. In step 860,server(s) 310 execute an automated DNS command updating the zone file toinclude the email address, the tertiary domain or the DNS recordmodification.

After receiving and storing all sub domain registration settingsreceived by the registrant from the sub domain registration settingscontrol panel 400, server(s) 310 may receive a request from a potentialsub domain name registrar, via client(s) 320, to search the availabilityof, and/or register, a sub domain associated with the domain name.

In some embodiments, this request may comprise an HTTP request receivedfrom client(s) 320 via a hypertext link within the content of a web pagewithin a website. In some embodiments, the website may be a registrarwebsite, and in some embodiments, the website may be a website operatedby the registrant associated with the sub domain's domain name. In someembodiments, the sub domain registration control panel may comprise aweb page created by the registrar or registrant. In other embodiments,the sub domain registration control panel may be rendered by onregistrant websites via remote procedure call to an API on theregistrar's server, the remote procedure call causing the server torender, and the registrant's web page to display the

The website may include a web page specifically programmed with thedisclosed sub domain registration control panel 405 functionality. Inresponse to the HTTP request, server(s) 310 may render the sub domainregistration control panel 405 and transmit it to client(s) 320, whichmay display it on an Internet browser or other client display software.FIG. 9, for example, demonstrates a sub domain registration controlpanel 405, which may comprise a plurality of HTML form elements.

In some embodiments, prior to rendering the sub domain registrationcontrol panel 405 (or possibly the link requesting sub domainregistration on the website), server(s) 310 may execute a database queryreturning one or more data records associated with the domain nameand/or registrant to determine if the registrant selected the HTML formelement agreeing to transfer the domain name to the registrar if thedomain name is surrendered by the registrant. If not, the process mayend without rendering the sub domain registration control panel 405. Insome embodiments, server(s) 310 may transmit a notification to theregistrant with the reasons the control panel 405 wasn't rendered.

The sub domain registration control panel 405 may include anycombination of HTML form elements allowing the registrant to input a subdomain or any other tertiary domain to be searched and/or registered inassociation with the domain name. On submission of the HTML form dataand transmission from client(s) 320 to server(s) 110, server(s) 310 mayexecute a query of the zone file for the domain name, or any related DNSfiles, to identify the requested sub domain within the zone file or DNSfiles (e.g., in A records or NS records). In some embodiments, as eachsub domain is registered, server(s) 310 may execute a database query toinsert a record into a database of registered sub domains. In theseembodiments, on submission of the HTML form data and transmission fromclient(s) 320 to server(s) 110, server(s) 310 may execute a databasequery for any records containing data for the requested sub domain.

If the query identifies the sub domain within the zone file or relatedDNS file, or if the database query returns at least one recordcontaining data for the requested sub domain, server(s) 310 maydetermine that the sub domain is unavailable, and may render andtransmit a notice that the domain name is not available, which may bedisplayed on the sub domain registration control panel 405. Thepotential sub domain registrant may then input another desired domainname and repeat the process.

If the query does not identify the sub domain within the zone file orrelated DNS file, or if the database query does not return at least onerecord containing data for the requested sub domain, server(s) 310 maydetermine that the sub domain is available, and may render and transmita notice that the domain name is available, which may be displayed onthe sub domain registration control panel 405.

After determining that the desired sub domain is available, thepotential sub domain registrant may input additional information aboutthe domain name, such as DNS data identifying an IP address of a serverto which an NS record within the domain name zone file, or an A recordwithin a newly generated SLD zone file, as described below, shouldredirect in response to an HTTP request for the sub domain. The subdomain registration control panel 405 may include any combination ofHTML form elements allowing the registrant to input this DNS data.

On submission of the HTML form data and transmission from client(s) 320to server(s) 110, server(s) 310 may authenticate the user according toany prerequisites, as described herein, and may execute any necessarydatabase queries to update any proprietary registrar's data records inthe registrar database 330

Server(s) 310 may then create a DNS structure for the registered subdomain. The DNS structure may be created in one of a plurality of ways.In one embodiment, server(s) 310 may create an A record, within the zonefile for the associated domain name, that responds to incoming HTTPrequests for the sub domain by directing the HTTP request to the IPaddress for a website reflected in the A record. The DNS may thenredirect these requests to the appropriate IP address and website.

In another embodiment, server(s) 310 may automatically generate a subdomain zone file (which defines the DNS provider for the sub domainrather than returning an A record) including an A record within the subdomain zone file that responds to incoming HTTP requests for the subdomain by directing the HTTP request to the IP address for a websitereflected in the A record. The DNS may then redirect these requests tothe appropriate IP address and website. The server(s) 310 may thenupdate an NS record within the zone file for the associated domain name,so that DNS responds to incoming HTTP requests for the sub domain byreferencing the NS record (rather than returning an A record in thedomain name zone file), handling the redirection to the sub domain zonefile, and directing the HTTP request to the IP address within the subdomain zone file for a website reflected in a sub domain zone file's Arecord. The DNS may then redirect these requests to the appropriate IPaddress and website.

FIG. 10 demonstrates a sub domain settings control panel 435, which maybe available to the sub domain registrant after registering the subdomain. In some embodiments, as server(s) 310 render the sub domaincontrol panel 435, the HTML form elements may be displayed or notaccording to the data records within the data table defining featuresavailable to the sub domain registrant according to the registrarselections 440 from the sub domain registration settings control panel400. Server(s) 310 may receive selections from the sub domain settingscontrol panel 435, and update registrar data records and/or DNS recordsto reflect additional email, additional tertiary domains or update DNSsettings in the sub domain zone file.

The steps included in the embodiments illustrated and described inrelation to FIGS. 1-10 are not limited to the embodiment shown and maybe combined in several different orders and modified within multipleother embodiments. Although disclosed in specific combinations withinthese figures, the steps disclosed may be independent, arranged andcombined in any order and/or dependent on any other steps orcombinations of steps.

Other embodiments and uses of the above inventions will be apparent tothose having ordinary skill in the art upon consideration of thespecification and practice of the invention disclosed herein. Thespecification and examples given should be considered exemplary only,and it is contemplated that the appended claims will cover any othersuch embodiments or modifications as fall within the true scope of theinvention.

The Abstract accompanying this specification is provided to enable theUnited States Patent and Trademark Office and the public generally todetermine quickly from a cursory inspection the nature and gist of thetechnical disclosure and in no way intended for defining, determining,or limiting the present invention or any of its embodiments.

The invention claimed is:
 1. A system comprising: a first clientcomputer coupled to a network and running a first Internet browserdisplaying a first hypertext markup language (HTML) form on a sub domainregistration settings control panel; a second client computer coupled tothe network and running a second Internet browser displaying a secondHTML form on a sub domain registration control panel; and at least oneprocessor executing instructions causing a server computer, coupled tothe network, to: render the sub domain registration settings controlpanel; transmit the sub domain registration settings control panel,through the network, to a first client computer for display on the firstInternet browser; receive, from a registrant of a domain name, via thefirst HTML form, at least one user data defining at least one rule orprerequisite that must be fulfilled prior to a sub domain registrantbeing qualified to register a sub domain; execute a database querystoring, within a database coupled to the network, the at least one userdata defining the at least one rule or prerequisite; render the subdomain registration control panel; transmit the sub domain registrationcontrol panel, through the network, to the second client computer fordisplay on the second Internet browser; receive, from a sub domainregistrant, via the second HTML form, a transmission encoding: a subdomain registration request; the sub domain to be registered inassociation with the domain name; an Internet protocol (IP) address towhich a domain name system (DNS) directs a hypertext transfer protocol(HTTP) request for the sub domain; and an authentication verifying thatthe at least one rule or prerequisite has been fulfilled; responsive toreceiving the authentication, execute an automated DNS command insertingthe IP address into an address record within a zone file for the domainname; or a name server record within the zone file for the domain name.2. The system of claim 1, wherein the at least one user data comprisesat least one parameter defining the at least one rule or prerequisite.3. The system of claim 1, wherein the at least one user data comprises:at least one pre-defined parameter for the at least one rule orprerequisite: defined within at least one data record in the database;and selected by the registrant from the first HTML form; or a customizedsoftware defining the at least one pre-defined parameter for the atleast one rule or prerequisite.
 4. The system of claim 1, wherein the atleast one user data comprises: a code entered into the first HTML form,the code having been received via an SMS message, an email, a postcardor a phone call; and an email address verified by the server computer.5. The system of claim 1, wherein the instructions cause the servercomputer to: query the database for a data record comprising anauthentication challenge; render the authentication challenge on the subdomain registration control panel; transmit the sub domain registrationcontrol panel to the second client computer for display; receive achallenge response to the authentication challenge via the second HTMLform; compare the challenge response with a correct challenge responsein the data record; and responsive to the challenge response matchingthe correct challenge response, authenticate that the at least one ruleor prerequisite has been fulfilled.
 6. The system of claim 1, whereinthe instructions cause the server computer to receive from theregistrant, via an HTML form element on the first HTML form, a selectionacknowledging that, responsive to the domain name being surrendered bythe registrant, the domain name will be transferred to the registrar. 7.A system comprising at least one processor executing instructionscausing a server computer, coupled to a network, to: render a firstcontrol panel comprising a first web page form; transmit the firstcontrol panel, through the network, to a first client computer fordisplay on a first client display software running on the first clientcomputer; receive, from a registrant of a domain name, via the first webpage form, at least one user data defining at least one rule orprerequisite that must be fulfilled prior to a sub domain registrantbeing qualified to register a sub domain; execute a database querystoring, within a database coupled to the network, the at least one userdata defining the at least one rule or prerequisite; render a secondcontrol panel comprising a second web page form; transmit the secondcontrol panel, through the network, to a second client computer fordisplay on a second client display software running on the second clientcomputer; receive, from a sub domain registrant, via the second web pageform, a transmission encoding: a sub domain registration request; thesub domain to be registered in association with the domain name; anInternet protocol (IP) address to which a domain name system (DNS)directs a hypertext transfer protocol (HTTP) request for the sub domain;and an authentication verifying that the at least one rule orprerequisite has been fulfilled; responsive to receiving theauthentication, execute an automated DNS command inserting the IPaddress into an address record within a zone file for the domain name;or a name server record within the zone file for the domain name.
 8. Thesystem of claim 7, wherein the at least one user data comprises at leastone parameter defining the at least one rule or prerequisite.
 9. Thesystem of claim 7, wherein the at least one user data comprises: atleast one pre-defined parameter for the at least one rule orprerequisite: defined within at least one data record in the database;and selected by the registrant from the first web page form; or acustomized software defining the at least one pre-defined parameter forthe at least one rule or prerequisite.
 10. The system of claim 7,wherein the at least one user data comprises: a code entered into thefirst web page form, the code having been received via an SMS message,an email, a postcard or a phone call; and an email address verified bythe server computer.
 11. The system of claim 7, wherein the instructionscause the server computer to: query the database for a data recordcomprising an authentication challenge; render the authenticationchallenge on the second control panel; transmit the second control panelto the second client computer for display; receive a challenge responseto the authentication challenge via the second web page form; comparethe challenge response with a correct challenge response in the datarecord; and responsive to the challenge response matching the correctchallenge response, authenticate that the at least one rule orprerequisite has been fulfilled.
 12. The system of claim 7, wherein theinstructions cause the server computer to receive from the registrant,via a form element on the first web page form, a selection acknowledgingthat, responsive to the domain name being surrendered by the registrant,the domain name will be transferred to the registrar.
 13. A methodcomprising the steps of: rendering, by a server computer coupled to anetwork, a first control panel comprising a first web page form;transmitting, by the server computer, the first control panel, throughthe network, to a first client computer for display on a first clientdisplay software running on the first client computer; receiving, by theserver computer, from a registrant of a domain name, via the first webpage form, at least one user data defining at least one rule orprerequisite that must be fulfilled prior to a sub domain registrantbeing qualified to register a sub domain; execute a database querystoring, within a database coupled to the network, the at least one userdata defining the at least one rule or prerequisite; render a secondcontrol panel comprising a second web page form; transmit the secondcontrol panel, through the network, to a second client computer fordisplay on a second client display software running on the second clientcomputer; receive, from a sub domain registrant, via the second web pageform, a transmission encoding: a sub domain registration request; thesub domain to be registered in association with the domain name; anInternet protocol (IP) address to which a domain name system (DNS)directs a hypertext transfer protocol (HTTP) request for the sub domain;and an authentication verifying that the at least one rule orprerequisite has been fulfilled; responsive to receiving theauthentication, execute an automated DNS command inserting the IPaddress into an address record within a zone file for the domain name;or a name server record within the zone file for the domain name. 14.The method of claim 13, wherein the at least one user data comprises atleast one parameter defining the at least one rule or prerequisite. 15.The method of claim 13, wherein the at least one user data comprises: atleast one pre-defined parameter for the at least one rule orprerequisite: defined within at least one data record in the database;and selected by the registrant from the first web page form; or acustomized software defining the at least one pre-defined parameter forthe at least one rule or prerequisite.
 16. The method of claim 13,wherein the at least one user data comprises: a code entered into thefirst web page form, the code having been received via an SMS message,an email, a postcard or a phone call; and an email address verified bythe server computer.
 17. The method of claim 13, further comprising thesteps of: querying, by the server computer, the database for a datarecord comprising an authentication challenge; rendering, by the servercomputer, the authentication challenge on the second control panel;transmitting, by the server computer, the second control panel to thesecond client computer for display; receiving, by the server computer, achallenge response to the authentication challenge via the second webpage form; comparing, by the server computer, the challenge responsewith a correct challenge response in the data record; and responsive tothe challenge response matching the correct challenge response,authenticating, by the server computer, that the at least one rule orprerequisite has been fulfilled.
 18. The method of claim 13, furthercomprising the step of receiving, by the server computer, from theregistrant, via a form element on the first web page form, a selectionacknowledging that, responsive to the domain name being surrendered bythe registrant, the domain name will be transferred to the registrar.